The pyramid will display all the sides in one complete rotation. To revisit any of the sides, click the arrows to rotate the pyramid. To view the descriptions, roll your mouse over the levels.
The Twelve XP Practices
Twelve XP Practices
Twelve XP Practices
Practice signifying writing user stories, estimating effort, and gaining team commitment towards iteration. Planning game is used for each iteration and for overall release with participation from customer and team.
The practice of iteratively releasing functionality incrementally to the customer focusing constantly on the MMFs. Such small releases engages customer creating a feedback loop towards fine tuning.
Involves system thinking applying design patterns and a set of development practices increasing shared understanding of the code facilitatingestimation in iteration planning.
The practice of flexibility in designing a scalable solution towards changing requirements. The goal is to focus on efficiency. As XP focuses on small releases, simple design is highly emphasized in eXtreme Programming.
The practice of test driven development is important in eXtreme Programming where test cases are written prior to any code development to ensure that the code is written to pass the test.
The reorganization of the working code to bring the organization in line with its functionality and make it more maintainable with noticeable effect on functionality or performance.
The practice of having two developers working on the code. This approach improves the productivity and efficiency unearthing defects earlier increasing shared code ownership. The pair can be different throughout the project.
The practice of distributing responsibility and accountability of code quality to the whole team through peer reviews. The focus is to hold the entire team share the responsibility to avoid any central dependency.
The practice of maintaining a consistent pace throughout the project. Using timeboxing principles promoted by velocity and commitment driven planning, the team maintains a consistent pace delivering customer value.
The practice recommending the customer representation on site to increase the high-bandwidth communication enabling developing user stories and acceptance tests for functionality.
The practice of integrating the code completed immediately for testing leading to faster defect resolution. This continous integration and deployment can be automated and happen many times on a single day.
Establishing best practices not limiting to file and folder names, variable naming convetions, indentations, braces, documentation, exception handling, and audit logs augmenting shared code ownership.
Planning Game
Iterative Planning
Systems Thinking
Simple Design
TDD
Continous Improvement
Pair Programming
Collective Code Ownership
Sustainable Pace
On-Site Client
Contiuous Integration
Coding Standards
(c) Agile Training Champions. Developed by Dr. Sriram Rajagopalan. All rights reserved
